-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(backend,shared,clerk-js): Support suffixed cookies [CORE-2086] #3506
Open
dimkl
wants to merge
11
commits into
main
Choose a base branch
from
CORE-2086/suffixed-cookies-draft
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 254c96c The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
11 tasks
f12aaa0
to
7dcea49
Compare
7dcea49
to
50ca6e3
Compare
50ca6e3
to
6a7c065
Compare
6a7c065
to
976ae21
Compare
colinclerk
reviewed
Jun 6, 2024
0655a51
to
da8dd2b
Compare
e05b4b2
to
c6335a2
Compare
dc8b9f4
to
02c6f00
Compare
b6a8f19
to
98113a7
Compare
…cookies This change is required to support setting both suffixed/un-suffixed cookies using part of the publishableKey to support Multiple apps running on the same eTLD+1 domain or localhost. Setting both suffixed/un-suffixed cookies is used to support backwards compatibility.
The optionsAssertions module will include assertion function for options used across our package
…ence in AuthenticateContext
…g client_uat / session
…de@18 missing crypto.subtle
…secure context To avoid bundling the whole crypto-js library we used dynamic imports to load the dependency only if required and subpath imports to allow treeshake add only the required code parts from the crypto-js
98113a7
to
254c96c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Generate suffixed and un-suffixed
__client_uat
(in dev instance),__session
,__clerk_db_jwt
(In dev instance) cookies from ClerkJS and support reading the either the suffixed or the un-suffixed cookies in the backend SDK using the__client_uat
&__session
cookies.New ClerkJS versions will generate both suffixed and un-suffixed cookies but the backend SDK will consume only 1 of those 2.
Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change